Java: Replaced getStackTrace() calls with printStackTrace() calls #7497
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
Java-v1
scmacdon
approved these changes
Jun 30, 2025
scmacdon
added
On Call Review complete
scmacdon
force-pushed
the
fix-stacktrace-typos
branch
from
8262a37 to
d780e27
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed that in some places
getStackTrace()is called instead ofprintStackTrace().getStackTrace()returns an array whileprintStackTrace()goes about actually printing it to System.err. So essentially, in instances wheregetStackTrace()is called, an array is returned yet not stored, and the pertinent stack trace is never output.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.